Add support for @custom-variant
#1127
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RobinMalfait
approved these changes
Jan 21, 2025
- v4 doesn’t have `@screen` - `@apply` doesn’t make sense to suggest top-level - `@tailwind` doesn’t make sense to suggest in v4 — we want people to use the imports instead - Things like `@config`, `@plugin`, `@source` etc… all must be top-level
thecrypticace
force-pushed
the
feat/add-support-for-custom-variant
branch
from
e9563db to
a7e06a6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for
@custom-variant, adds variant suggestions for@variant, and tweaks when at-rules are suggested such that only ones that are valid in the given context should be suggested (e.g. when at the root or when nested in some rule).This is the IntelliSense portion of tailwindlabs/tailwindcss#15663